Skip to content

release: 0.68.1#128

Open
stainless-app[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk
Open

release: 0.68.1#128
stainless-app[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.68.1 (2026-06-17)

Full Changelog: v0.68.0...v0.68.1

Bug Fixes

  • client: send content-type header for requests with an omitted optional body (2cde4eb)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions


Note

Low Risk
Small, targeted change to request body/header assembly with no API surface changes beyond the patch version bump.

Overview
Release 0.68.1 bumps package version metadata (package.json, src/version.ts, release manifest) and documents the patch in CHANGELOG.md.

The functional change is a client HTTP fix in buildBody: when an operation defines a request body but the caller leaves an optional body out (body is null/undefined yet 'body' in options), the client now runs the request through the JSON encoder so Content-Type: application/json is still sent. Operations with no body at all (e.g. GET/DELETE) continue to omit body headers as before.

Reviewed by Cursor Bugbot for commit 224b078. Bugbot is set up for automated code reviews on this repo. Configure here.

@firetiger-agent

Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: This is an automated release PR for kernel-node-sdk (a Node.js SDK), not a code change to a service within the kernel repo itself; unclear which logical service this impacts or if deploy monitoring applies to SDK releases.

To monitor this PR anyway, reply with @firetiger monitor this.

@stainless-app

stainless-app Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/kernel-typescript/2cde4eb8a2469ffe31bad3462e9c3e3339d9bd7c/dist.tar.gz'

Expires at: Fri, 17 Jul 2026 02:10:36 GMT
Updated at: Wed, 17 Jun 2026 02:10:36 GMT

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 224b078. Configure here.

Comment thread src/client.ts
// content-type for those, and only elide it for operations with no body at
// all (e.g. GET/DELETE).
if (body == null && 'body' in options) {
return this.#encoder({ body, headers: buildHeaders([rawHeaders]) });

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Null body sends JSON null

Low Severity

The new optional-body branch uses body == null, so an explicit null body (e.g. apiKeys.rotate(id, null)) runs through #encoder and JSON.stringify(null) becomes the string "null", which is attached to the fetch. Omitted optional bodies are undefined and correctly get Content-Type without a body; null now sends a literal JSON null entity, which differs from pre-change behavior and from the stated fix for omitted params.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 224b078. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants